Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable28] fix(migration): Make naming constraint fail softer on updates #43445

Merged
merged 1 commit into from
Feb 8, 2024

Conversation

backportbot[bot]
Copy link

@backportbot backportbot bot commented Feb 8, 2024

Backport of PR #43357

Only on installation we want to break hard, so that all developers notice
the bugs when installing the app on any database or CI, and can work on
fixing their migrations before releasing a version incompatible with Postgres.

In case of updates we might be running on production instances and the
administrators being faced with the error would not know how to resolve it
anyway. This can also happen with instances, that had the issue before the
current update, so we don't want to make their life more complicated
than needed.

Signed-off-by: Joas Schilling <[email protected]>
@backportbot backportbot bot added bug 3. to review Waiting for reviews labels Feb 8, 2024
@backportbot backportbot bot added this to the Nextcloud 28.0.3 milestone Feb 8, 2024
@szaimen szaimen merged commit 32fbcd3 into stable28 Feb 8, 2024
50 checks passed
@szaimen szaimen deleted the backport/43357/stable28 branch February 8, 2024 11:15
@skjnldsv skjnldsv mentioned this pull request Feb 14, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants